Method for determining an interruption source

ABSTRACT

A testing method to discern an original source with respect to the interruption, suitable for use in a computer system is provided. The computer system includes an integrated drive electronics (IDE) bus and a peripheral component interconnect (PCI) bus. The IDE bus is connected to a testing IDE device and the standard IDE device. The PCI bus includes a plurality of input/output (I/O) ports. First, one of the I/O ports is set up with a testing flag and a command is issued to the testing IDE device. After then, the interruption sent from the testing IDE device or the standard IDE device is received. Next, it is checked whether or not the testing flag is set. If it is, then it can be determined that the interruption is coming from the testing IDE device. The present invention can discern the interruption, which is coming from which one of the correct source, under the protection mode or the real mode, so as to be helpful for testing.

[0001] This application incorporates by reference of Taiwan application Serial No. 090120769, filed Aug. 23, 2001.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This invention relates to a method for determining an interruption source, and more particularly, the invention relates to a test method for determining an interruption source, which is issued by an integrated drive electronics device.

[0004] 2. Description of Related Art

[0005] The integrated drive electronics (IDE) device is nowadays commonly used as a peripheral device of a computer system, such as the hard disk drive or the CD/DVD-ROM optical disc drive. In the personal computer system, each of the IDE buses can be used to connect two IDE devices, which are respectively positioned at a primary bus of the IDE bus and a secondary bus of the IDE bus. Since the command set being used is different, The IDE devices can also be divided into types of the ATA device and the ATAPI device. The ATA device includes for example a hard disk device, and the ATAPI device for example includes CD/DVD-ROM optical disc drive, optical rewriteable disc drive, and ZIP disk drive. The command set that is used to access the ATA device, is the ATA command, and the command set that is used to access the ATAPI device, is the ATAPI command. As shown in FIG. 1A, it is a drawing, schematically illustrating a command flow diagram for proceeding the data access from the host to the IDE device. In FIG. 1A, the IDE device is a type of the ATAPI device, and the command set being used is the ATAPI command. Also referring to FIG. 1B at the same time, it is a drawing schematically illustrating an action flow diagram of the IDE device for responding to the commands made by the host. At the first, the host issues a pre-command to the IDE device. This pre-command is a content of 0xA0 in the ATAPI command, as shown in the step 102. As the IDE device receives this pre-command, as shown in the step 104, then it is checked to know whether or not the IDE de is busy, as shown in the step 106. If it is not busy, then an interruption, which can also receive the command, is issued, so as to inform the host, which can start to issue the access command to the IDE device, as shown in the step 108. When the host receives the interruption from the IDE device being able to receive the command, then the host makes the access command to the IDE device, as shown in the step 110. This access command is a packet command with a size of 12 bytes. The content of this command includes, for example, the data read from IDE device or the data written into the IDE device. When the IDE device receives the access command issued by the host, then the access command is executed. For example, the data of the IDE device is read out and is stored in the buffer region, as shown in the step 112. After that, an interruption, indicating the access being ready, is issued as shown in the step 114. When the host receives the interruption for access, then the host starts to access the IDE device, as shown in the step 116. After the access is finished, the IDE device issues again an interruption for stopping the command, as shown in the step 118.

[0006] When the IDE device has been accomplished in development, it needs a test program to perform a test on the IDE device. At this stage, this IDE device is called a testing IDE device. The test program includes a simulation program and a testing interruption service routine (ISR). All of the interruptions issued by the IDE device are intercepted by the testing ISR. After the simulation program issues a command to a testing IDE device, responding an interruption. The testing ISR is necessary to intercept this interruption. After the testing process is performed, it returns again to the simulation program. However, if the testing IDE device and another standard IDE device are respectively connected to the same IDE bus at the master position and the slave position, then the testing ISR can not discern the received interruption, which is issued by which one of the IDE devices, and then therefore it cannot be known whether or not a testing process is necessary. The solution in the conventional method is, for example, that before the simulation program is to issue the command to the testing IDE device, a flag is determined beforehand. Also and, after the testing ISR receives the interruption, it first goes to check this flag to see whether or not the flag has been set. If it is, then it indicates that the interruption being received is the issued from the testing IDE device. The test program is operated under the Microsoft disk operation system (MS-DOS). In the real mode, it can only access the memory device by a size of 640K bytes. If a larger memory device is necessary to be accessed, then it should enter the protection mode. It cannot be shared for the memory devices respectively used in the protection mode and in the real mode.

[0007] However, the testing IDE device could be issuing the interruption under the real mod and the protection mode, but the simulation program does execute and set up the flag under the protection mode. If the testing IDE device issues the interruption under the real mode, the testing ISR will not be able to detect flag set by the simulation program, thereby it cannot be judged whether or not the interruption is issued by the testing IDE device.

SUMMARY OF THE INVENTION

[0008] It is therefore an objective of the present invention to provide a testing method for discerning which one is the original source with respect to the interruption under protection mode or the real mode.

[0009] In accordance with the foregoing and other objectives of the present invention, the invention provides a testing method to discern an original source with respect to the interruption, suitable for use in a computer system. The computer system includes an integrated drive electronics (IDE) bus and a peripheral component interconnect (PCI) bus. The IDE bus is connected to a testing IDE device and the standard IDE device. The PCI bus includes a plurality of input/output (I/O) ports. First, one of the I/O ports is set with a testing flag and a command is issued to the testing IDE device. After then, the interruption sent from the testing IDE device or the standard IDE device is received. Next, it is checked whether or not the testing flag is set. If it is, then it can be determined that the interruption is coming from the testing IDE device.

BRIEF DESCRIPTION OF DRAWINGS

[0010] The invention can be more fully understood by reading the following detailed description of the preferred embodiments, with reference made to the accompanying drawings, wherein:

[0011]FIG. 1A is a diagram drawing, schematically illustrating a command flow diagram for proceeding the data access from the host to the IDE device;

[0012]FIG. 1B is a diagram drawing, schematically illustrating an action flow diagram of the IDE device for responding to the commands made by the host; and

[0013]FIG. 2 is a diagram drawing, schematically illustrating a flow diagram of a testing method to determine the original source with respect to the interruption, according to a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0014]FIG. 2 is a diagram drawing, schematically illustrating a flow diagram of a testing method to determine the original source with respect to the interruption, according to a preferred embodiment of the present invention. This method has the application on a computer system. The computer system includes an integrated drive electronics (IDE) bus and a peripheral component interconnect (PCI) bus. The IDE bus is connected to a testing IDE device and the standard IDE device. The PCI bus includes a plurality of input/output (I/O) ports. When an IDE device has been developed at the final stage, it needs a test program being performed to test this IDE device. This IDE device usually is called a testing IDE device. The test program can include a simulation program includes a simulation program, a testing interruption service routine (ISR), and a judging interruption service routine. At the initial stage, it needs first to redirect the interruption, which is issued by the IDE device, to the judging ISR. This also means that the interruptions issued by all of the IDE devices will be received by the judging ISR. First, the simulation program will set up a testing flag at one of the I/O ports and also issues a command to the testing IDE device, as shown in the step 204. After then, the judging ISR receives the interruption issued by the IDE device, as shown in the step 206. Then, the judging ISR checks whether or not the testing flag has been set up, as shown in the step 208. If it is, then it means that the received interruption can be determined that the interruption is issued by the testing IDE device, also and the testing flag is released as shown in the step 210. After then, the next step 212 is performed. In the step 212, the judging ISR is driving the testing ISR to execute the subsequent testing procedure.

[0015] The test program is operated under the Microsoft disk operation system (MS-DOS). In the real mode, it can only access the memory device by a size of 640K bytes. If a larger memory device is necessary to be accessed, then it should enter the protection mode. It cannot be shared for the memory devices respectively used in the protection mode and in the real mode. However, the testing IDE device could be issuing the interruption under the real mod or the protection mode, but the simulation program does execute and set up the flag under the protection mode. Since the I/O port on the PCI bus can be shared for reading and writing under the protection mode and the real mode. Therefore, the present invention sets up the testing flag on the I/O port of the PCI bus, so as to assure that all of the interruptions issued by the testing IDE device under the real mode or the protection mode can be received by the test program and can be judged to known the original source with respect to the interruptions, and can be helpful for performing test.

[0016] In summary of the present invention, the method disclosed in the foregoing preferred embodiment of the present invention for judging the original sources responsible for the interruptions can judge the original source with respect to the received interruption under the protection mode or the real mode.

[0017] The invention has been described using exemplary preferred embodiments. However, it is to be understood that the scope of the invention is not limited to the disclosed embodiments. On the contrary, it is intended to cover various modifications and similar arrangements. The scope of the claims, therefore, should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. 

What is claimed is:
 1. A method for determining a source with respect to an interruption, suitable for use between an integrated drive electronics (IDE) bus and a peripheral component interconnect (PCI) bus, wherein said IDE bus is connected to a standard IDE device and a testing IDE device, said PCI bus including a plurality of input/output (I/O) ports, said method comprising: setting up a testing flag at one of said I/O ports, and having a command to the testing IDE device; receiving an interruption, which is issued by said IDE devices; and checking whether or not said testing flag has been set up, wherein if it is, said interruption is determined as said one issued from said testing IDE device.
 2. The method as recited in claim 1, wherein said testing flag is set up at one of said I/O ports at said number of 0x81.
 3. The method as recited in claim 1, wherein said testing flag is set up at one of said I/O ports at said number of 0x80.
 4. The method as recited in claim 1, wherein said testing IDE device can be a CD/DVD-ROM optical disc drive.
 5. The method as recited in claim 1, wherein said step of setting up said testing flag on one of said I/O ports and issuing a command to a testing IDE device is performed under a protection mode.
 6. The method as recited in claim 1, wherein said interruption is issued under a protection mode, and at this moment said step of checking whether or not said testing flag has been set up, wherein if it is, said interruption is determined as said one issued from said testing IDE device is performed under said protection mode.
 7. The method as recited in claim 1, wherein said interruption is issued under a real mode, and at this moment said step of checking whether or not said testing flag has been set up, wherein if it is, said interruption is determined as said one issued from said testing IDE device is performed under said real mode.
 8. A method for determining a source with respect to an interruption, used for detecting an interruption signal of an integrated drive electronics (IDE) device, wherein said characteristic is to set up a testing flag at an I/O port of a peripheral component interconnect (PCI) bus, so as to assure that all of interruption signals issued by said IDE device under a real mode and under a protection mode can be received and be judged where is said original source coming from for said interruption signals.
 9. The method as recited in claim 8, wherein said testing flag is using a simulation program to perform.
 10. The method as recited in claim 8, wherein said interruption signals are received by a testing interruption service routine (ISR).
 11. The method as recited in claim 8, wherein said method for determining said source of said interruption signals further comprise the step of: checking whether or not said testing flag has been set up, wherein if it is, said interruption is determined as said one issued from said testing IDE device. 